Apparatus and method for running application in mobile terminal

ABSTRACT

An apparatus and method for running an application in a mobile terminal are provided. The apparatus includes a display for running a second application on a first screen according to a second touch event, and displaying a second screen smaller than the first screen, and a controller for hiding the second screen from a current screen to display an entire area of the first screen while a touch in an external area of the second screen is detected, and displaying again the second screen on the first screen if the touch in the external area of the second screen is released.

PRIORITY

This application claims the benefit under 35 U.S.C. §119(a) of a KoreanPatent Application filed in the Korean Intellectual Property Office onSep. 20, 2011 and assigned Serial No. 10-2011-0094588, the entiredisclosure of which is hereby incorporated by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an apparatus and method for runningapplications in a mobile terminal. More particularly, the presentinvention relates to an apparatus for running an application and methodcapable of quickly running applications in a mobile terminal.

2. Description of the Related Art

Due to recent advances in mobile terminal technology, mobile terminalsare increasingly used to run or execute a wide variety of applications.In order for a user to make or generate a note having information aboutan application on a mobile terminal while running the application, theuser may run or execute a memo application after terminating theapplication for which a note is to be generated, and then generates thenote having the information using the memo application.

Furthermore, in order for the user to review the information about theapplication while, in the memo application, making the note having theinformation about the application, the user may need to again executethe application after terminating the memo application. As stated above,while making the note having the information about the application inthe memo application, the user may be inconvenienced by repeatedlyrunning and terminating the applications on which the note is about.

SUMMARY OF THE INVENTION

Aspects of the present invention are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentinvention is to provide an application running apparatus and methodcapable of quickly running applications in a mobile terminal.

Another aspect of the present invention is to provide an apparatus forrunning an application and method capable of quickly switching betweenapplications in a mobile terminal.

Another aspect of the present invention is to provide an apparatus forrunning an application and method capable of allowing a user to easilysee the contents on a background screen while running an application ona screen window.

Another aspect of the present invention is to provide an apparatus forrunning an application and method for using data executed on a screenwindow for running an application, as data for another application.

In accordance with one aspect of the present invention, an apparatus forrunning an application in a mobile terminal is provided. The apparatusincludes a display for running a second application on a first screenaccording to a second touch event, and displaying a second screensmaller than the first screen, and a controller for hiding the secondscreen from a current screen to display an entire area of the firstscreen while a touch in an external area of the second screen isdetected, and displaying again the second screen on the first screen ifthe touch in the external area of the second screen is released.

In accordance with another aspect of the present invention, an apparatusfor running an application in a mobile terminal is provided. Theapparatus includes a display for displaying, in a semi-transparentwindow, a second screen on which a second application is run accordingto a second touch event, on a first screen on which a first applicationis run according to a first touch event, to display the first screenthrough the second screen, and a controller for, when an input actionoccurs on the second screen, banning an operation associated with theinput action from being performed on the first screen under the secondscreen, and performing the operation associated with the input action onthe second screen.

In accordance with another aspect of the present invention, an apparatusfor running an application in a mobile terminal is provided. Theapparatus includes a display for displaying on a current screen anobject for running an application corresponding to a type of a toucheven, and a controller for displaying an object for running anapplication according to a type of a touch event, and hiding the objectin response to a touch event having occurred in an external area of theobject while displaying the object.

In accordance with further another aspect of the present invention, amethod for running an application in a mobile terminal is provided. Themethod includes, running a second application on a first screenaccording to a second touch event, and displaying a second screensmaller than the first screen, hiding the second screen from a currentscreen to display an entire area of the first screen while a touch in anexternal area of the second screen is detected, and displaying again thesecond screen on the first screen if the touch in the external area ofthe second screen is released.

In accordance with yet another aspect of the present invention, a methodfor running an application in a mobile terminal is provided. The methodincludes, displaying, in a semi-transparent window, a second screen onwhich a second application is run according to a second touch event, ona first screen on which a first application is run according to a firsttouch event, to display the first screen through the second screen, andwhen an input action occurs on the second screen, banning an operationassociated with the input action from being performed on the firstscreen under the second screen, and performing the operation associatedwith the input action on the second screen.

In accordance with yet another aspect of the present invention, a methodfor running an application in a mobile terminal is provided. The methodincludes, if a touch event occurs, displaying an object for running anapplication according to a type of the touch event having occurred, andhiding the object if a touch event occurs in an external area of theobject while displaying the object. Other aspects, advantages, andsalient features of the invention will become apparent to those skilledin the art from the following detailed description, which, taken inconjunction with the annexed drawings, discloses exemplary embodimentsof the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainexemplary embodiments of the present invention will be more apparentfrom the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates a structure of a mobile terminal according to anexemplary embodiment of the present invention;

FIGS. 2A and 2B illustrate a process of running an application in amobile terminal according to an exemplary embodiment of the presentinvention;

FIGS. 3A to 3C illustrate a process of running a memo application duringInternet access in a mobile terminal according to an exemplaryembodiment of the present invention;

FIGS. 4A to 4C illustrate a process of running a memo application duringuse of a messenger application in a mobile terminal according to anexemplary embodiment of the present invention;

FIGS. 5A to 5D illustrate a process of running a memo application in astandby mode in a mobile terminal according to an exemplary embodimentof the present invention;

FIGS. 6A and 6B illustrate a process of running a memo applicationduring use of a message application in a mobile terminal according to anexemplary embodiment of the present invention; and

FIGS. 7A and 7B illustrate a process of running a memo applicationduring use of an e-mail application in a mobile terminal according to anexemplary embodiment of the present invention.

Throughout the drawings, like reference numerals will be understood torefer to like parts, components, and structures.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of exemplaryembodiments of the invention as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skilled in the art will recognize thatvarious changes and modifications of the embodiments described hereincan be made without departing from the scope and spirit of theinvention. In addition, descriptions of well-known functions andconstructions are omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of theinvention. Accordingly, it should be apparent to those skilled in theart that the following description of exemplary embodiments of thepresent invention is provided for illustration purpose only and not forthe purpose of limiting the invention as defined by the appended claimsand their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

FIG. 1 illustrates a structure of a mobile terminal according to anexemplary embodiment of the present invention.

Referring to FIG. 1, a Radio Frequency (RF) unit 123 provides radiocommunications for the mobile terminal. The RF unit 123 includes an RFtransmitter (not shown) for frequency up-converting of transmissionsignals and amplifying the up-converted signals, and an RF receiver (notshown) for low-noise-amplifying of received signals and frequencydown-converting the amplified signals. A data processor 120 includes atransmitter for encoding and modulating the transmission signals, and areceiver for demodulating and decoding the received signals. In otherwords, the data processor 120 may include a modem and a codec. The codecincludes a data codec for processing packet data, and an audio codec forprocessing audio signals such as voice or other similar audio signals.An audio processor 125 plays received audio signals output from theaudio codec of the data processor 120 using a speaker SPK, and transferstransmission audio signals picked up by a microphone MIC to the audiocodec in the data processor 120.

A key input unit 127 includes keys for inputting numeric and textinformation and function keys for setting various functions. However,the present invention is not limited thereto, and the mobile terminalmay include a touchscreen or other similar elements for inputtingnumeric and text information.

A memory 130 may include a program memory and data memory. The programmemory may store programs for controlling the general operation of themobile terminal. The data memory may temporarily store the datagenerated during execution of these programs. The memory 130 may storeinformation about types of executable applications, associated withtypes of touch events.

According to the present exemplary embodiment of the present invention,the memory 130 may store a control program for displaying a separatescreen window for running an application according to a type of a touchevent having occurred on the touch screen so as to run the application.The memory 130 may store a control program for hiding the screen windowin response to a touch event that has occurred in an external area ofthe screen window while the separate screen window for running anapplication is displayed, and displaying the screen window if the touchevent is terminated.

A controller 110 controls the overall operation of the mobile terminal.The controller 110 displays a screen window for running an applicationaccording to a type of a touch event having occurred on the touch screenso as to run the application, and hides the screen window in response toa touch event that has occurred in an external area of the screen windowwhile displaying the screen window. The controller 110 may display aseparate window by overlapping the screen window for running theapplication on the current screen. In other words, the controller 110may display the application in a separate window that is displayed ontop of other windows of the screen window.

While displaying the screen window for running the application accordingto the type of the touch event having occurred, if a touch event occurson the screen window, then the controller 110 exits, i.e., stopsdisplaying, the screen window on which the touch event has occurred, anddisplays a screen window for running an application corresponding to thetype of the touch event having occurred.

While displaying the screen window for running the application accordingto the type of the touch event having occurred, if a touch event occurson the screen window, then the controller 110 displays a list ofapplications, exits the screen window on which the touch event hasoccurred, and then displays a screen window for running an applicationselected from the list of applications displayed by the controller 110.If the touch event that occurred in an area of the screen other than thescreen window for running the application is terminated due to a type ofthe touch event, then the controller 110 displays the screen window.

While hiding the screen window for running the application according tothe type of the touch event having occurred, if an application isselected on the current screen by a drag event that occurred while thetouch event is maintained, then the controller 110 stores data executedon the screen window as data for the application selected by the touchand drag events, and at the same time, stops displaying the hiddenscreen window.

While hiding the screen window for running the application according tothe type of the touch event having occurred, the controller 110 updatesthe application. The controller 110 may update only synchronizableapplications, and may update the applications only if theirsynchronization time is longer than a time period from the time thescreen window was displayed till the time the screen window was hidden.However, the present invention is not limited thereto, and thecontroller 110 may update applications in any suitable manner.

While displaying the screen window for running the application accordingto the type of the touch event having occurred, the controller 110 mayupdate the application, or the controller 110 may update the applicationwhen the screen window is exited or no longer displayed.

The controller 110 may display the screen window for running theapplication in a semi-transparent manner depending on the type of thetouch event having occurred. When the screen window is displayed in asemi-transparent manner, the user may run the application in thesemi-transparent screen window while viewing the contents displayed onthe background screen. As to a user's input action occurring on theactivated semi-transparent screen window, the action is performed onlyon the screen window without affecting the background screen or theitems, elements or applications displayed on the background screen.While displaying the screen window for running the application accordingto the type of the touch event having occurred, if an exit button or keyis selected or an exit command input on the screen window, then thecontroller 110 stops displaying the screen window for running theapplication.

A camera 140 includes a camera sensor for capturing images by capturingan optical image signal and converting the captured optical image signalinto an electrical signal that may be an analog image signal or adigital image signal. The camera 140 also includes a signal processorfor converting the analog image signal captured by the camera sensorinto digital data. The camera sensor may be a Charge-Coupled Device(CCD) or Complementary Metal-Oxide-Semiconductor (CMOS) sensor, and thesignal processor may be implemented with a Digital Signal Processor(DSP). However, the present invention is not limited thereto, and thecamera sensor and the signal processor may be implemented in anysuitable manner. The camera sensor and the signal processor may beimplemented either in an integrated way, or in a separated way.

An image processor 150 performs Image Signal Processing (ISP) fordisplaying the image signals output from the camera 140 on a display160. The ISP performs functions such as gamma correction, interpolation,spatial variations, image effects, image scaling, Automatic WhiteBalance (AWB), Automatic Exposure (AE), and Automatic Focus (AF), andother similar image processing operations and functions. The imageprocessor 150 processes the image signals output from the camera 140 ona frame-by-frame basis, and outputs the frame image data according tocharacteristics and a size of the display 160. The image processor 150includes a video codec, which compresses the frame image data displayedon the display 160 according to a preset coding scheme, and decompressesthe compressed frame image data into the original frame image data. Thevideo codec may include a Joint Photographic Experts Group (JPEG) codec,a Moving Picture Experts Group 4 (MPEG4) codec, a Wavelet codec, or anyother similar video codec. The image processor 150 includes an On-ScreenDisplay (OSD) function, and may output OSD data according to the size ofthe screen displayed under control of the controller 110.

The display 160 includes a screen (not shown) for displaying imagesignals output from the image processor 150 and user data output fromthe controller 110. The display 160 may be a Liquid Crystal Display(LCD), an Organic Light Emitting Diode (OLED) display, or any othersuitable display type. In the case of the LCD, the display 160 mayinclude an LCD controller, a memory capable of storing image data, andan LCD panel. When the screen of the display 160 is implemented in as atouch screen, the LCD or other suitable display type may serve as aninput unit. In this case, keys such as the key input unit 127 may bedisplayed on the display 160.

In accordance with the present exemplary embodiment of the presentinvention, the display 160 displays a separate window by overlapping thescreen window for running the application on the current screenaccording to the type of the touch event having occurred to run theapplication.

The operation of running an application in a mobile terminal will bedescribed in detail below with reference to FIGS. 2A to 7B.

FIGS. 2A and 2B illustrate a process of running an application in amobile terminal according to an exemplary embodiment of the presentinvention.

Referring to FIGS. 1, 2A and 2B, if a touch event to run an applicationoccurs in the mobile terminal in step 201, then, in step 202, thecontroller 110 determines a type of the touch event having occurred anddisplays a screen window A for running an application according to thetype of the touch event having occurred. In step 202, the controller 110determines a type of the application corresponding to the type of thetouch event having occurred using the memory 130, and then displays aseparate window by overlapping the screen window A for running thedetected application on the current screen of the display 160.

The type of the touch event may be determined according to the number oftouch inputs and the touch input time, i.e., an amount of time for whichthe touch input occurs. In a case where a stylus pen is used, the typeof the touch event may be determined according to the number of touchinputs and the touch input time, which occur when a button mounted onthe stylus pen is input or pressed.

While displaying the screen window A in step 202, the controller 110determines, in step 203, whether a touch event to run an applicationoccurs in an area of the screen window A. If a touch event occurs on thescreen window A, then, in step 204, the controller 110 determines a typeof the application corresponding to the type of the touch event havingoccurred using the memory 130, stops displaying the screen window A, anddisplays a separate window by overlapping a screen window B for runningthe detected application on the current screen.

Although not shown in FIG. 2, while displaying the screen window A instep 202, if a touch event to run an application occurs in an area ofthe screen window A, the controller 110 may display a list ofapplications, and if an application is selected from the applicationlist, the controller 110 may exit the screen window A and display aseparate window by overlapping a screen window for running the selectedapplication on the current screen.

While displaying the screen window A in step 202, the controller 110, instep 205, determines whether a touch event occurs in an external area ofthe screen window A. If a touch event occurs in an external area of thescreen window A, then the controller 110 hides the screen window A byinactivating it in step 206. A type of the touch event for hiding thescreen window A by inactivating it may be a variety of touch inputactions. Therefore, the screen window A is hidden while the touch inputaction is maintained in then external area of the screen window A, sothat the user may view the contents on the background screen of thescreen window A.

While hiding the screen window A in step 206, the controller 110, instep 207, determines whether the touch event is terminated, i.e., thetouch input is not maintained. If so, then in step 208, the controller110 displays again the screen window A on the current screen byactivating it. In steps 205 to 208, by repeating the displaying andhiding of the screen window A in response to the touch event, the usermay run the application on the screen window A while viewing thecontents on the background screen of the screen window A.

If the touch event having occurred is maintained in step 207 while thescreen window A is hidden in step 206, then the controller 110determines whether a drag event occurs in step 209. If a drag eventoccurs, then in step 210, the controller 110 determines whether anapplication is selected by the touch and drag events. If an applicationis selected by the touch and drag events, the controller 110 stores thedata executed on the screen window A as data for the applicationselected by the touch and drag events and exits or stops displaying thescreen window A in step 211.

For example, if a recipient is selected from a list of contacts providedby messaging or e-mail applications by touch and drag events on thecurrent screen, which is the screen through which the controller 110runs a message application after hiding the screen window A, then thememo data executed on the screen window A may be stored as data for therecipient, or may be stored as attached data in a message or e-mail thatis sent to the recipient after the controller 110 automatically switchesto a message/e-mail mode or switches to the messaging or e-mailapplications. For example, if a date is selected from a list of datesprovided by a calendar application by touch and drag events on thecurrent screen on which the controller 110 runs the calendar applicationafter hiding the screen window A, then the memo data executed on thescreen window A may be stored as data corresponding to the selecteddate.

As another example, if an icon representing a type of an application,such as a message application, e-mail application and an albumapplication, is selected by touch and drag events on the current screenfor which the controller 110 is in an standby mode after hiding thescreen window A, then the memo data executed on the screen window A maybe stored as attached data after the controller 110 switches to amessage or e-mail mode, or the memo data may be stored as datacorresponding to an image selected from the album.

While hiding the screen window A in step 206, the controller 110 updatesapplications installed in the mobile terminal in step 212. Moreparticularly, in step 212, the controller 110 updates synchronizableapplications, and may update the applications only if theirsynchronization time is longer than a time period starting from a timeat which the screen window A was displayed until a time at which thescreen window A was hidden. While displaying the screen window A, thecontroller 110 may update the applications, or the controller 110 mayupdate the applications only when the screen window A is exited.

For example, when the mobile terminal is set to update an applicationonly in the state where the screen window A is hidden, if the screenwindow A for running a memo application is displayed so as to overlapwith the current screen of a messenger application that is currentlyrunning, then the controller 110 does not update the application.Thereafter, if the screen window A is hidden, then the controller 110compares a synchronization time for the messenger application with atime period from when the time the screen window A was displayed untilthe time when the screen window A was hidden, in order to update thesynchronizable messenger application. For example, if a synchronizationtime for the messenger application is set as ‘5 seconds’ and a timeperiod from the time when the screen window A was displayed until thetime when the screen window A was hidden is ‘3 seconds’, i.e., thesynchronization time for the messenger application, that being 5seconds, is longer than the time period from when the time the screenwindow A was displayed until the time when the screen window A washidden, that being 3 seconds, then the controller 110 updates themessenger application. For example, the controller 110 may display theconversations made while the screen window A is seen, thereby preventingthe update from frequently occurring every time the screen window A ishidden.

If updating of the application is set to occur in the state where thescreen window A is hidden, then the controller 110 may update thesynchronizable messenger application and display it on the backgroundscreen when displaying the screen window A, which is for displaying thememo application, on the current screen in an overlapping manner.

If updating of the application is set to occur only when the screenwindow A is exited, then the controller 110 may update thesynchronizable messenger application and display it when the screenwindow A is completely exited and while displaying the screen window Aon the current screen displaying the messenger application in anoverlapping manner.

While displaying the screen window A in step 202, the controller 110, instep 213, determines whether an exit button, key or input is selected onthe screen window A. If the exit button, key or input is selected on thescreen window A, the controller 110 exits or stops displaying the screenwindow A in step 214.

The operation of displaying and hiding the screen window in response tothe touch event in FIGS. 2A and 2B will be described with reference toFIGS. 3A to 7B.

FIGS. 3A to 3C illustrate a process of running a memo application duringInternet access in a mobile terminal according to an exemplaryembodiment of the present invention.

Referring to FIGS. 3A to 3C, while the user views an article, image,video, or website over the Internet, as shown in FIG. 3A, if a touchevent to run the memo application occurs on the screen displaying thearticle, regardless of the area at which the touch event occurs on thescreen, then a separate window may be displayed by overlapping a screenwindow 161 for running the memo application on the current screendisplaying the article, as shown in FIG. 3B. While displaying the screenwindow 161, if a touch event (i.e., a touch input) occurs and ismaintained in an external area of the screen window 161 on the entirescreen, then the screen window 161 may be hidden, as shown in FIG. 3C,allowing the user to view the current screen displaying the article.While hiding the screen window 161, as shown in FIG. 3C, if the touchevent having occurred is terminated, then a separate window may bedisplayed again so as to overlap the screen window 161 on the currentscreen, as shown in FIG. 3B.

FIGS. 4A to 4C illustrate a process of running a memo application duringuse of a messenger application in a mobile terminal according to anexemplary embodiment of the present invention.

Referring to FIGS. 4A to 4C, while running a messenger application, asshown in FIG. 4A, if a touch event to run the memo application occurs onthe screen displaying the messenger application, regardless of the areaat which the touch event occurs, for example, if two touch inputs occurcontinuously within a predetermined time, then a separate window may bedisplayed so as to overlap the screen window 161 for running the memoapplication on the current screen displaying the running of themessenger application, as shown in FIG. 4B.

While displaying the screen window 161, as shown in FIG. 4B, if a touchevent occurs and is maintained in an area of the screen other than thearea displaying the screen window 161, then the screen window 161 may behidden, as shown in FIG. 4C, thus, allowing the user to view the currentscreen displaying the messenger application. When updating of theapplication is set to occur only in the state where the screen window161 is hidden, if a synchronization time for the messenger applicationis longer than a time period from the time when the screen window 161was displayed until the time when the screen window was hidden, themessenger application is updated in the state where the screen window161 is hidden, as shown in FIG. 4C, and thus, it is possible to displaythe conversations made while the screen window 161 is displayed. If thetouch input having occurred is terminated while in the state shown inFIG. 4C, then the screen window 161 may be displayed again, as shown inFIG. 4B.

FIGS. 5A to 5D illustrate a process of running a memo application in astandby mode in a mobile terminal according to an exemplary embodimentof the present invention.

Referring to FIGS. 5A to 5D, in a standby mode, as shown in FIG. 5A, ifa touch event to run a memo application occurs, then a separate windowis displayed so as to overlap the screen window 161 for running the memoapplication on the standby mode screen as shown in FIGS. 5B and 5C.

While displaying the screen window 161, as shown in FIGS. 5B and 5C, ifa touch event occurs and is maintained in an area of the screen otherthan the area displaying the screen window 161, then the screen window161 is hidden and the standby screen is displayed, as shown in FIG. 5D.If the touch input having occurred is terminated while in the stateshown in FIG. 5D, then the screen window 161 is again displayed, asshown in FIGS. 5B and 5C.

If updating of the application is set to occur only in the state wherethe screen window 161 is hidden, then updating of a time widget from adisplayed time of ‘07:11’ to the current time ‘07:12’ is not performedwhile the screen window 161 is displayed, as shown in FIG. 5C. Ifupdating of the application is set only to occur when the screen window161 is exited, updating the displayed time of ‘07:11’ of the time widgetto the current time ‘07:12’ is not performed even while the screenwindow 161 is hidden, as shown in FIG. 5D.

FIGS. 6A and 6B illustrate a process of running a memo applicationduring use of a message application in a mobile terminal according to anexemplary embodiment of the present invention.

Referring to FIGS. 6A and 6B, if a touch event corresponding toexecuting a memo application occurs on a current screen displaying themessage application, then a separate window is displayed by overlappingthe screen window 161 for running the memo application on the currentscreen displaying the message application, as shown in FIG. 6A. Whiledisplaying the screen window 161, as shown in FIG. 6A, if a touch eventoccurs and is maintained in an area of the screen other than the areadisplaying the screen window 161, then the screen window 161 is hiddenand the current screen displaying the message application is displayed,as shown in FIG. 6B. If the touch input is terminated while in a stateshown in FIG. 6B, then the screen window 161 may be displayed again, asshown in FIG. 6A.

FIGS. 7A and 7B illustrate a process of running a memo applicationduring use of an e-mail application in a mobile terminal according to anexemplary embodiment of the present invention.

Referring to FIGS. 7A and 7B, if a touch event corresponding toexecuting the memo application occurs on the current screen displayingan e-mail application, then a separate window is displayed byoverlapping the screen window 161 for running the memo application onthe current screen displaying the e-mail application, as shown in FIG.7A.

While displaying the screen window 161, as shown in FIG. 7A, if a touchevent occurs and is maintained in an area of the screen other than thearea displaying the screen window 161, then the screen window 161 ishidden, and the current screen displaying the e-mail application isdisplayed, as shown in FIG. 7B. If the touch input is terminated whilein a state shown in FIG. 7B, then the screen window 161 may be displayedagain, as shown in FIG. 7A.

As is apparent from the foregoing description, the present exemplaryembodiments of an application running apparatus and method for a mobileterminal may quickly run, execute and switch between user-desiredapplications, and allow the user to easily view the contents of thebackground screen while running the application on the screen window. Inaddition, the present exemplary embodiments of an application runningapparatus and method may use the data executed on a screen window forrunning an application as data for another application.

While the invention has been shown and described with reference tocertain exemplary embodiments thereof, it will be understood by thoseskilled in the art that various changes in form and details may be madetherein without departing from the spirit and scope of the invention asdefined by the appended claims and their equivalents.

What is claimed is:
 1. An apparatus for running an application in amobile terminal, comprising: a display for running a second applicationon a first screen according to a second touch event, and displaying asecond screen smaller than the first screen; and a controller for hidingthe second screen from a current screen to display an entire area of thefirst screen while a touch in an external area of the second screen isdetected, and displaying again the second screen on the first screen ifthe touch in the external area of the second screen is released.
 2. Theapparatus of claim 1, wherein the second application is a memoapplication, and the memo application receives an input action after thetouch in the external area of the second screen is released.
 3. Theapparatus of claim 1, wherein a screen for the second application isdisplayed in a different size or shape according to a type of a touchevent.
 4. The apparatus of claim 1, wherein the second touch eventcorresponds to an action in which two touch inputs occur consecutivelywhile a button mounted on a stylus pen is pushed.
 5. The apparatus ofclaim 1, wherein the first screen is a standby screen or a screen onwhich a first application is run according to a first touch event.
 6. Anapparatus for running an application in a mobile terminal, comprising: adisplay for displaying, in a semi-transparent window, a second screen onwhich a second application is run according to a second touch event, ona first screen on which a first application is run according to a firsttouch event, to display the first screen through the second screen; anda controller for, when an input action occurs on the second screen,banning an operation associated with the input action from beingperformed on the first screen under the second screen, and performingthe operation associated with the input action on the second screen. 7.An apparatus for running an application in a mobile terminal,comprising: a display for displaying on a current screen an object forrunning an application corresponding to a type of a touch event; and acontroller for displaying an object for running an application accordingto a type of a touch event, and hiding the object in response to a touchevent having occurred in an external area of the object while displayingthe object.
 8. The apparatus of claim 7, wherein if the touch event torun an application occurs, the controller displays an object for runningan application corresponding to a type of the touch event havingoccurred, on a current screen in an overlapping way.
 9. The apparatus ofclaim 7, wherein if a touch event occurs on the object while displayingthe object, the controller exits the object being displayed, anddisplays an object for running an application corresponding to a type ofthe touch event having occurred.
 10. The apparatus of claim 7, whereinif a touch event occurs on the object while displaying the object, thecontroller displays a list of applications, exits the object beingdisplayed, and then displays an object for running an applicationselected from the list of applications.
 11. The apparatus of claim 7,wherein if the touch event having occurred in an external area of theobject is terminated, the controller displays again the object.
 12. Theapparatus of claim 7, wherein if an application is selected on a currentscreen by a drag event having occurred with the touch event maintainedin a state where the object is hidden, the controller stores dataexecuted on the object as data for the application selected by the touchand drag events, and exits the hidden object.
 13. The apparatus of claim7, wherein the controller updates the application in a state where theobject is hidden.
 14. The apparatus of claim 7, wherein if an exit isselected on the object while displaying the object, the controller exitsthe object for running an application.
 15. A method for running anapplication in a mobile terminal, comprising: running a secondapplication on a first screen according to a second touch event, anddisplaying a second screen smaller than the first screen; hiding thesecond screen from a current screen to display an entire area of thefirst screen while a touch in an external area of the second screen isdetected; and displaying again the second screen on the first screen ifthe touch in the external area of the second screen is released.
 16. Themethod of claim 15, wherein the second application is a memoapplication, and the memo application receives an input action after thetouch in the external area of the second screen is released.
 17. Themethod of claim 15, wherein a screen for the second application isdisplayed in a different size or shape according to a type of a touchevent.
 18. The method of claim 15, wherein the second touch eventcorresponds to an action in which two touch inputs occur consecutivelywhile a button mounted on a stylus pen is pushed.
 19. The method ofclaim 15, wherein the first screen is a standby screen or a screen onwhich a first application is run according to a first touch event.
 20. Amethod for running an application in a mobile terminal, comprising:displaying, in a semi-transparent window, a second screen on which asecond application is run according to a second touch event, on a firstscreen on which a first application is run according to a first touchevent, to display the first screen through the second screen; and whenan input action occurs on the second screen, banning an operationassociated with the input action from being performed on the firstscreen under the second screen, and performing the operation associatedwith the input action on the second screen.
 21. A method for running anapplication in a mobile terminal, comprising: if a touch event occurs,displaying an object for running an application according to a type ofthe touch event having occurred; and hiding the object if a touch eventoccurs in an external area of the object while displaying the object.22. The method of claim 21, further comprising: if the touch eventoccurs, displaying an object for running an application corresponding toa type of the touch event having occurred, on a current screen in anoverlapping way.
 23. The method of claim 21, further comprising: if atouch event occurs on the object while displaying the object, exitingthe object being displayed; and displaying an object for running anapplication corresponding to a type of the touch event having occurred.24. The method of claim 23, further comprising: if a touch event occurson the object while displaying the object, displaying a list ofapplications; and if an application is selected from the list ofapplication, exiting the object being displayed, and then displaying anobject for running the selected application.
 25. The method of claim 21,further comprising: if the touch event having occurred in an externalarea of the object is terminated, displaying again the object.
 26. Themethod of claim 21, further comprising: if an application is selected ona current screen by a drag event having occurred with the touch eventmaintained in a state where the object is hidden, storing data executedon the object as data for the application selected by the touch and dragevents; and exiting the hidden object.
 27. The method of claim 21,further comprising updating the application in a state where the objectis hidden.
 28. The method of claim 21, further comprising: if an exit isselected on the object while displaying the object, exiting the objectfor running an application.